-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add OidcTestClient #36110
Add OidcTestClient #36110
Conversation
f87d243
to
9c7f2d4
Compare
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
9c7f2d4
to
c7f419f
Compare
Hey @gastaldi @pedroigor Have a look please next week, this is a simple test client as an alternative to KeycloakTestClient. If we have a non-Keycloak provider, then the only option is a Wiremock based integration testing. Will update the Auth0 tutorial afterwards |
I removed it from the backports as parts of it rely on other changes (it doesn't compile in 3.4). Moreover it really looks like a new feature so I think it's better to wait for 3.5. Let me know if you think otherwise. |
The main motivation is to help Auth0 or other SaaS OIDC users to test against live test domains, where
quarkus.oidc.auth-server-url
is pointing to some US or EU domain. The only other options for such cases is testing with Wiremocks and unit testing with@TestSecurity
. In fact this will also work for Keycloak test realms, wherequarkus.oidc.auth-server-url
is pointing to them, without depending on Dev Services for Keycloak.It also fixes #30080.
After some time I've confirmed today I can write a test against the Auth0 domain which is covered in #35931.
So once this PR is ready for review and is approved, I'll update #35931.